Skip to content

Adding Offload Test into DXC build pipeline#8584

Open
joaosaffran wants to merge 3 commits into
microsoft:mainfrom
joaosaffran:vk-release/build-test-pipeline
Open

Adding Offload Test into DXC build pipeline#8584
joaosaffran wants to merge 3 commits into
microsoft:mainfrom
joaosaffran:vk-release/build-test-pipeline

Conversation

@joaosaffran

@joaosaffran joaosaffran commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

This patch adds a new stage into DXC build pipeline, it runs the offload-test agains the built binaries, it uses WARP for DXIL and lava-pipe for SPIRV builds.

Part of: microsoft/hlsl-specs#886

@joaosaffran joaosaffran force-pushed the vk-release/build-test-pipeline branch 6 times, most recently from 2959f34 to 6c3d8b4 Compare June 24, 2026 20:32
@joaosaffran joaosaffran force-pushed the vk-release/build-test-pipeline branch from 6c3d8b4 to fad2cb9 Compare June 24, 2026 20:32
@joaosaffran joaosaffran changed the title [DO NOT REVIEW] Adding VK into nightly build Adding Offload Test into DXC build pipeline Jun 24, 2026
@joaosaffran joaosaffran marked this pull request as ready for review June 24, 2026 20:39
Comment thread azure-pipelines.yml Outdated
variables:
LAVAPIPE_VERSION: '26.1.2'
WARP_VERSION: '1.0.19'
VS_DEV: 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\Build\vcvars64.bat'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't hardcode this string. We should be able to reuse some of the logic in the other scripts to find this.

Comment thread azure-pipelines.yml Outdated
- task: BatchScript@1
displayName: 'Set up MSVC environment'
inputs:
filename: '$(VS_DEV)'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does hctstart.cmd actually do this for you? Might be a way to avoid hard coding the script path?

Comment thread azure-pipelines.yml
displayName: 'DXIL Compat Suite Tests (1.8 point release)'
condition: succeededOrFailed()

- script: |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For PR builds, I'm wondering if we should only do this if the PR has a particular label on it? I don't think we'll want to gate all PRs on this since it'll add significant time to the builds.

@github-project-automation github-project-automation Bot moved this from New to In progress in HLSL Roadmap Jun 24, 2026
Comment thread azure-pipelines.yml Outdated
$dst = "$(Build.ArtifactStagingDirectory)\dxc"
New-Item -ItemType Directory -Force -Path $dst | Out-Null
foreach ($f in @("dxc.exe","dxv.exe","dxcompiler.dll","dxil.dll")) {
if (Test-Path "$bin\$f") { Copy-Item "$bin\$f" $dst } else { Write-Warning "missing $f" }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of logging a warning, should we fail if one of the files doesn't exist?

Comment thread azure-pipelines.yml Outdated
condition: succeededOrFailed()
variables:
LAVAPIPE_VERSION: '26.1.2'
WARP_VERSION: '1.0.19'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are hard coded versions intentional? I worry about needing to consistently bump these versions.

@joaosaffran joaosaffran added the run-offload-tests trigger offload-tests on a given pr label Jun 25, 2026
@joaosaffran

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

run-offload-tests trigger offload-tests on a given pr

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

4 participants